CI: include answer-progress Playwright journey in production UI gate#793
CI: include answer-progress Playwright journey in production UI gate#793BigSimmo wants to merge 7 commits into
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
📝 WalkthroughWalkthroughPlaywright production test matching now includes the answer-progress and additional UI tool specs. CI scope detection and self-tests classify the answer-progress smoke test as UI, source, and coverage scope, with the verification outcome recorded in the review ledger. ChangesProduction UI coverage
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@playwright.config.ts`:
- Around line 15-16: Update productionSpecPattern in the Playwright
configuration to include the ui-tools-collapse and ui-tools-task-directory spec
alternatives, keeping it aligned with testMatch and the production UI gate
scope.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 5c2ee264-5361-4dd8-8ef8-397df0550f13
📒 Files selected for processing (3)
docs/branch-review-ledger.mdplaywright.config.tsscripts/ci-change-scope.mjs
| /.*(?:answer-progress-ui-smoke|ui-(smoke|stress|accessibility|tools|overlap|universal-search|specifiers|formulation|pwa))\.spec\.ts/; | ||
| const mockupSpecPattern = /.*ui-(tools|tools-collapse|tools-task-directory)\.spec\.ts/; |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Keep the production matcher aligned with testMatch.
Line 15 still omits ui-tools-collapse and ui-tools-task-directory, although Line 22 and the PR objective include both. If the Chromium production project uses productionSpecPattern, those specs will remain excluded from the production UI gate. Add both alternatives here or explicitly remove them from the production-scope objective.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@playwright.config.ts` around lines 15 - 16, Update productionSpecPattern in
the Playwright configuration to include the ui-tools-collapse and
ui-tools-task-directory spec alternatives, keeping it aligned with testMatch and
the production UI gate scope.
…s-playwright-db17
…s-playwright-db17
…s-playwright-db17
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #3107 (cancelled). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
Pull request was closed
Summary
tests/answer-progress-ui-smoke.spec.tsspec to Playwright selection inplaywright.config.tsso the production UI gate covers answer-progress safety assertions.scripts/ci-change-scope.mjsto classify edits to that spec as UI-affecting, closing a verification gap where assertion edits could slip past the required Chromium UI job.Verification
node scripts/ci-change-scope.mjs --self-testpassed.node scripts/ci-change-scope.mjs --json --files tests/answer-progress-ui-smoke.spec.tsreportsui_changed: true.Risk and rollout
Summary by CodeRabbit
Bug Fixes
Documentation